systemd: Make timeline.timer persistent #388
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Without this, timeline snapshots might not be taken for up to 59 minutes after boot. This is troublesome for laptops and other use cases where the user might not have their machine on for that long.
mrkline
force-pushed
the
more-timely-systemd-timers
branch
from
924e78b to
37155fc
Compare
Member
|
I cannot remember why the cleanup.timer is setup that way. Maybe to avoid extra IO during boot. |
Author
|
Checking in a year later - @aschnell, are there objections to this change? Is there somewhere else I should try to get it upstream? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without this, timeline snapshots might not be taken for up to 59
minutes after boot. This is troublesome for laptops and other use cases
where the user might not have their machine on for that long.
On a less pressing, but related note, why doesn't
cleanup.timerrun for ten minutes after system startup? (If the main concern is to make sureboot.timerhas been run before, wouldn't a minute or two suffice?)